stm32 ospi driver : run application in external flash memory XIP #93032
Conversation
Define with CONFIG_FLASH_BASE_ADDRESS when the external flash is on an octoSPI node : "st,stm32-ospi" compatible Signed-off-by: Francois Ramu <francois.ramu@st.com>
FRASTM
force-pushed
the
stm32u5_xip
branch
2 times, most recently
from
d02c1a8 to
f4991ef
Compare
MCUboot mode should not be set on MCUboot side in my opinion, it should be set on Zephyr side using Sysbuild (SB_CONFIG_MCUBOOT_MODE_DIRECT_XIP) at the board or app level so that the setting is propagated properly to both MCUboot and App builds. |
Add the octoSPI 2 which is connection to a octo NOR flash mx25lm51245 on the stm32u585 disco kit. Define the partition on the 64MBytes space of the external flash in the specific dts file (not the _ns one) Use the STM32Cube programmer to flash with the corresponding external loader for XiP mode. Do not mass-erase the internal flash when flashing. Removing usb_device will avoid test feature for that board. Signed-off-by: Francois Ramu <francois.ramu@st.com>
Add the OSPI 1 which is an octoSPI connection to a octo NOR flash mx25lm51245 on the stm32u585 disco kit. Define the partition on the 64MBytes space of the external flash. Use the STM32Cube programmer to flash with the corresponding external loader for XiP mode. Do not mass-erase the internal flash when flashing. Removing usb_device will avoid test feature for that board. Signed-off-by: Francois Ramu <francois.ramu@st.com>
|
Define the partition of the external octo NOR in the b_u858i_iot02a.dts to avoid conflit with the partitioning of the b_u858i_iot02a_ns.dts. |
Run the sample to execute in place on the external flash of the b_u585i_iot02a or stm32h7b3i disco kit, with_boot application is built and linked for the external flash Signed-off-by: Francois Ramu <francois.ramu@st.com>
There was a problem hiding this comment.
For boards that have enough space/sectors in internal Flash to be used without MemMapped external Flash (with or without MCUboot), I think it makes more sense to create a board variant for the App in Ext Flash usecase.
This way, both configurations can be tested in CI without need for extra overlays..., and users will have ready-to-use configurations to choose from depending on their requirements. This will make the conf on MCUboot side simpler as well.
|
FRASTM
changed the title
Following the stm32h5 run application in external flash memory XIP
This PR makes the samples/sysbuild/with_mcuboot --sysbuild running on the stm32u585 disco kit
Requires the ./bootloader/mcuboot/bootzephyr/boards/b_u585i_iot02a.conf :
run the
west build -p -b b_u585i_iot02a samples/sysbuild/with_mcuboot --sysbuildRequires boot/zephyr/boards/b_u585i_iot02a.conf